
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<HTML><HEAD><TITLE>Man page of XYMONNET</TITLE>
</HEAD><BODY>
<H1>XYMONNET</H1>
Section: User Commands  (1)<BR>Updated: Version 4.3.13:  7 Jan 2014<BR><A HREF="#index">Index</A>
<A HREF="../index.html">Return to Main Contents</A><HR>

<A NAME="lbAB">&nbsp;</A>
<H2>NAME</H2>

xymonnet - Xymon network test tool
<A NAME="lbAC">&nbsp;</A>
<H2>SYNOPSIS</H2>

<B>xymonnet [--ping|--noping] [--timeout=N] [options] [hostname] [hostname]</B>

<BR>

(See the OPTIONS section for a description of the available command-line options).
<P>
<A NAME="lbAD">&nbsp;</A>
<H2>DESCRIPTION</H2>

<I><A HREF="../man1/xymonnet.1.html">xymonnet</A>(1)</I>

handles the network tests of hosts defined in the Xymon configuration
file, hosts.cfg. It is normally run at regular intervals by 
<I><A HREF="../man8/xymonlaunch.8.html">xymonlaunch</A>(8)</I>

via an entry in the
<I><A HREF="../man5/tasks.cfg.5.html">tasks.cfg</A>(5)</I>

file.
<P>
xymonnet does all of the normal tests of TCP-based network
services (telnet, ftp, ssh, smtp, pop, imap ....) - i.e. 
all of the services listed in protocols.cfg. For
these tests, a completely new and very speedy service-
checker has been implemented.
<P>
xymonnet has built-in support for testing SSL-enabled
protocols, e.g. imaps, pop3s, nntps, telnets, if SSL-support
was enabled when configuring xymonnet. The full list of known
tests is found in the
<I><A HREF="../man5/protocols.cfg.5.html">protocols.cfg</A>(5)</I>

file in $XYMONHOME/etc/protocols.cfg.
<P>
In addition, it implements the &quot;dns&quot; and &quot;dig&quot; tests for
testing DNS servers.
<P>
xymonnet also implements a check for NTP servers - this test 
is called &quot;ntp&quot;. If you want to use it, you must define the
NTPDATE environment variable to point at the location of your
<I><A HREF="../man1/ntpdate.1.html">ntpdate</A>(1)</I>

program.
<P>
Note: xymonnet performs the connectivity test (ping) based on the
hostname, unless the host is tagged with &quot;testip&quot; or the 
&quot;--dns=ip&quot; option is used. So the target of the connectivity
test can be determined by your /etc/hosts file or DNS.
<P>
By default, all servers are tested - if XYMONNETWORK is set via
<I><A HREF="../man5/xymonserver.cfg.5.html">xymonserver.cfg</A>(5)</I>

then only the hosts marked as belonging to this network are
tested. If the command-line includes one or more hostnames,
then only those servers are tested.
<P>
<P>
<A NAME="lbAE">&nbsp;</A>
<H2>GENERAL OPTIONS</H2>

<P>
<DL COMPACT>
<DT>--timeout=N<DD>
Determines the timeout (in seconds) for each
service that is tested. For TCP tests (those from XYMONNETSVCS),
if the connection to the service does not succeed within N 
seconds, the service is reported as being down. For HTTP
tests, this is the absolute limit for the entire request
to the webserver (the time needed to connect to the server,
plus the time it takes the server to respond to the request).
Default: 10 seconds
<P>
<DT>--conntimeout=N<DD>
This option is deprecated, and will be ignored. Use the
--timeout option instead.
<P>
<DT>--cmdtimeout=N<DD>
This option sets a timeout for the external commands used for
testing of NTP and RPC services, and to perform traceroute.
<P>
<DT>--concurrency=N<DD>
Determines the number of network tests that
run in parallel. Default is operating system dependent,
but will usually be 256. If xymonnet begins to complain 
about not being able to get a &quot;socket&quot;, try running
xymonnet with a lower value like 50 or 100.
<P>
<DT>--dns-timeout=N (default: 30 seconds)<DD>
xymonnet will timeout all DNS lookups after N seconds.
Any pending DNS lookups are regarded as failed, i.e. the
network tests that depend on this DNS lookup will report
an error.
<BR>

Note: If you use the --no-ares option, timeout of DNS
lookups cannot be controlled by xymonnet.
<P>
<DT>--dns-max-all=N<DD>
Same as &quot;--dns-timeout=N&quot;. The &quot;--dns-max-all&quot; option is 
deprecated and should not be used.
<P>
<DT>--dns=[ip|only|standard]<DD>
Determines how xymonnet finds the IP adresses of the hosts to test. 
By default (the &quot;standard&quot;), xymonnet does a DNS lookup of the hostname 
to determine the IP address, unless the host has the &quot;testip&quot; 
tag, or the DNS lookup fails.
<BR>

With &quot;--dns=only&quot; xymonnet will ONLY do the DNS lookup;
if it fails, then all services on that host will be 
reported as being down.
<BR>

With &quot;--dns=ip&quot; xymonnet will never do a DNS lookup;
it will use the IP adresse specified in hosts.cfg for
the tests. Thus, this setting is equivalent to having
the &quot;testip&quot; tag on all hosts. Note that http tests
will ignore this setting and still perform a DNS
lookup for the hostname given in the URL; see the
&quot;xymonnet tags for HTTP tests&quot; section in
<I><A HREF="../man5/hosts.cfg.5.html">hosts.cfg</A>(5)</I>

<P>
<DT>--no-ares<DD>
Disable the ARES resolver built into xymonnet. This makes
xymonnet resolve hostnames using your system resolver
function. You should only use this as a last resort if xymonnet
cannot resolve the hostnames you use in the normal way (via DNS
or /etc/hosts). One reason for using this would be if you need to 
resolve hostnames via NIS/NIS+ (a.k.a. Yellow Pages).
<BR>

The system resolver function does not provide a mechanism for
controlling timeouts of the hostname lookups, so if your
DNS or NIS server is down, xymonnet can take a very long time
to run. The --dns-timeout option is effectively disabled when
using this option.
<P>
<DT>--dnslog=FILENAME<DD>
Log failed hostname lookups to the file FILENAME. FILENAME should 
be a full pathname.
<P>
<DT>--report[=COLUMNNAME]<DD>
With this option, xymonnet will send a status message with details 
of how many hosts were processed, how many tests were generated, 
any errors that occurred during the run, and some timing statistics. 
The default columnname is &quot;xymonnet&quot;.
<P>
<DT>--test-untagged<DD>
When using the XYMONNETWORK environment variable to test
only hosts on a particular network segment, xymonnet
will ignore hosts that do not have any &quot;NET:x&quot; tag.
So only hosts that have a NET:$XYMONNETWORK tag will be 
tested.
<BR>

With this option, hosts with no NET: tag are included
in the test, so that all hosts that either have a
matching NET: tag, or no NET: tag at all are tested.
<P>
<DT>--frequenttestlimit=N<DD>
Used with the
<I><A HREF="../man1/xymonnet-again.sh.1.html">xymonnet-again.sh</A>(1)</I>

Xymon extension. This option determines how long failed tests
remain in the frequent-test queue. The default is 1800
seconds (30 minutes).
<P>
<DT>--timelimit=N<DD>
Causes xymonnet to generate a warning if the run-time
of xymonnet exceeds N seconds. By default N is set to
the value of TASKSLEEP, so a warning triggers if the
network tests cannot complete in the time given for one
cycle of the xymonnet task. Apart from the warning, this 
option has no effect, i.e. it will not terminate xymonnet
prematurely. So to eliminate any such warnings, use this
option with a very high value of N.
<P>
<DT>--huge=N<DD>
Warn if the response from a TCP test is more than N bytes.
If you see from the xymonnet status report that you are
transferring large amounts of data for your tests, you can
enable this option to see which tests have large replies.
<BR>

Default: 0 (disabled).
<P>
<DT>--validity=N<DD>
Make the test results valid for N minutes before they go purple. 
By default test results are valid for 30 minutes; if you run xymonnet
less often than that, the results will go purple before the next run
of xymonnet. This option lets you change how long the status is 
valid.
<P>
<DT>--source-ip=IPADDRESS<DD>
On multi-homed hosts, this option can be used to explicitly
select the source IP address used for the network tests.
&quot;IPADDRESS&quot; must be a valid IP-address on the host running
xymonnet.
<P>
<DT>--loadhostsfromxymond<DD>
Instead of reading the hosts.cfg file, xymonnet will load the
hosts.cfg configuration from the xymond daemon. This eliminates
the need for reading the hosts.cfg, and if you have xymond and
xymonnet running on different hosts, it also eliminates the need
for copying the hosts.cfg file between systems. Note that the
&quot;netinclude&quot; option in hosts.cfg is ignored when this option is
enabled.
<P>
</DL>
<A NAME="lbAF">&nbsp;</A>
<H2>OPTIONS FOR TESTS OF THE SIMPLE TCP SERVICES</H2>

<DL COMPACT>
<DT>--checkresponse[=COLOR]<DD>
When testing well-known services (e.g. FTP, SSH, SMTP, POP-2, POP-3, 
IMAP, NNTP and rsync), xymonnet will look for a valid service-specific
&quot;OK&quot; response. If another reponse is seen, this will cause
the test to report a warning (yellow) status. Without this
option, the response from the service is ignored.
<BR>

The optional color-name is used to select a color other than
yellow for the status message when the response is wrong.
E.g. &quot;--checkresponse=red&quot; will cause a &quot;red&quot; status message
to be sent when the service does not respond as expected.
<P>
<DT>--no-flags<DD>
By default, xymonnet sends some extra information in the
status messages, called &quot;flags&quot;. These are used by xymongen
e.g. to pick different icons for reversed tests when
generating the Xymon webpages. This option makes
xymonnet omit these flags from the status messages.
<P>
<DT>--shuffle<DD>
By default, TCP tests run roughly in the order that the hosts
are listed in the hosts.cfg file. If you have many tests for
one server, this may result in an exceptionally large
load when Xymon is testing it because Xymon will perform
a lot of tests at the same time. To avoid this, the
<B>--shuffle</B> option reorders the sequence of tests
so they are spread randomly across all of the servers
tested.
<P>
</DL>
<A NAME="lbAG">&nbsp;</A>
<H2>OPTIONS FOR THE PING TEST</H2>

Note: xymonnet uses the program defined by the FPING
environment to execute ping-tests - by default, that is
the
<I><A HREF="../man1/xymonping.1.html">xymonping</A>(1)</I>

utility. See
<I><A HREF="../man5/xymonserver.cfg.5.html">xymonserver.cfg</A>(5)</I>

for a description of how to customize this, e.g. if you
need to run it with &quot;sudo&quot; or a similar tool.
<P>
<DL COMPACT>
<DT>--ping<DD>
Enables xymonnet's ping test. The column name used for
ping test results is defined by the PINGCOLUMN environment 
variable in 
<I><A HREF="../man5/xymonserver.cfg.5.html">xymonserver.cfg</A>(5).</I>

<BR>

If not specifed, xymonnet uses the CONNTEST environment
variable to determine if it should perform the ping test
or not. So if you prefer to use another tool to implement 
ping checks, either set the CONNTEST environment variable 
to false, or run xymonnet with the &quot;--noping&quot;.
<P>
<DT>--noping<DD>
Disable the connectivity test.
<P>
<DT>--trace<DD>
<DT>--notrace<DD>
Enable/disable the use of traceroute when a ping-test fails.
Performing a traceroute for failed ping tests is a slow
operation, so the default is not to do any traceroute, unless
it is requested on a per-host basis via the &quot;trace&quot; tag in the 
<I><A HREF="../man5/hosts.cfg.5.html">hosts.cfg</A>(5) </I>

entry for each host. The &quot;--trace&quot; option changes this, so 
the default becomes to run traceroute on all hosts where
the ping test fails; you can then disable it on specific 
hosts by putting a &quot;notrace&quot; tag on the host-entry.
<P>
<DT>--ping-tasks=N<DD>
Spread the task of pinging the hosts over N processes. If you have
a very large number of hosts the time it takes to ping all of them 
can be substantial, even with the use of tools like fping or xymonping
that ping many hosts in parallel. This option causes xymonnet to
start N separate ping processes, the IP's that are being ping'ed will
be divided evenly between these processes.
<P>
<P>
</DL>
<A NAME="lbAH">&nbsp;</A>
<H2>OPTIONS FOR HTTP (WEB) TESTS</H2>

<DL COMPACT>
<DT>--content=CONTENTTESTNAME<DD>
Determines the name of the column Xymon displays for content checks. 
The default is &quot;content&quot;.  If you have used the &quot;cont.sh&quot; or &quot;cont2.sh&quot; 
scripts earlier, you may want to use &quot;--content=cont&quot; to report content
checks using the same test name as these scripts do.
<DT>--bb-proxy-syntax<DD>
Adhere to the Big Brother syntax for a URL, which allows specifying 
a HTTP proxy as part of a URL. See <B>&quot;HTTP Testing via proxy&quot;</B> in the
<I><A HREF="../man5/hosts.cfg.5.html">hosts.cfg</A>(5) </I>

file for details. Beginning with Xymon 4.3.0, this behaviour is disabled
by default since URL's that include other URL's are now much more
common. This option restores the old Big Brother-compatible behaviour.
<P>
</DL>
<A NAME="lbAI">&nbsp;</A>
<H2>OPTIONS FOR SSL CERTIFICATE TESTS</H2>

<DL COMPACT>
<DT>--ssl=SSLCERTTESTNAME<DD>
Determines the name of the column Xymon displays for the SSL certificate checks.
The default is &quot;sslcert&quot;.
<DT>--no-ssl<DD>
Disables reporting of the SSL certificate check.
<P>
<DT>--sslwarn=N<DD>
<DT>--sslalarm=N<DD>
Determines the number of days before an SSL certificate
expires, where xymonnet will generate a warning or
alarm status for the SSL certificate column.
<P>
<DT>--sslbits=N<DD>
Enables checking that the encryption supported by the
SSL protocol uses an encryption key of at least N bits.
E.g. to trigger an alert if your SSL-enabled website 
supports less than 128 bits of encryption, use &quot;--sslbits=128&quot;.
Note: This can be enabled on a per-host basis using the
&quot;sslbits=N&quot; setting in 
<I><A HREF="../man5/hosts.cfg.5.html">hosts.cfg</A>(5)</I>

<P>
<DT>--sslkeysize=N<DD>
Enables checking of the length of the public key in SSL certificates.
N is the minimum size of the SSL public key, typically such keys
are 2048 bits, but some older certificates may use keys with 1024 bits
or less. If you specify this, SSL certificates with keys less than N
bits will result in the &quot;sslcert&quot; status going yellow.
Default: 0, i.e. this check is disabled.
<P>
<DT>--no-cipherlist<DD>
Do not show the list of encryption ciphers on the &quot;sslcert&quot; status.
<P>
<P>
</DL>
<A NAME="lbAJ">&nbsp;</A>
<H2>DEBUGGING OPTIONS</H2>

<DL COMPACT>
<DT>--no-update<DD>
Don't send any status updates to the Xymon server. Instead,
all messages are dumped to stdout.
<P>
<DT>--timing<DD>
Causes xymonnet to collect information about
the time spent in different parts of the program.
The information is printed on stdout just before
the program ends. Note that this information is also
included in the status report sent with the &quot;--report&quot;
option.
<P>
<DT>--debug<DD>
Dumps a bunch of status about the tests as they
progress to stdout.
<P>
<DT>--dump[=before|=after|=both]<DD>
Dumps internal memory structures before and/or after the
tests have executed.
<P>
<P>
</DL>
<A NAME="lbAK">&nbsp;</A>
<H2>INFORMATIONAL OPTIONS</H2>

<DL COMPACT>
<DT>--help or -?<DD>
Provide a summary of available command-line options.
<P>
<DT>--version<DD>
Prints the version number of xymonnet
<P>
<DT>--services<DD>
Dump the list of defined TCP services xymonnet knows
how to test. Do not run any tests.
<P>
<P>
</DL>
<A NAME="lbAL">&nbsp;</A>
<H2>USING COOKIES IN WEB TESTS</H2>

If the file $XYMONHOME/etc/cookies exist, cookies will be read from
this file and sent along with the HTTP requests when checking
websites. This file is in the Netscape Cookie format, see
<A HREF="http://www.netscape.com/newsref/std/cookie_spec.html">http://www.netscape.com/newsref/std/cookie_spec.html</A> for details
on this format. The
<I><A HREF="../man1/curl.1.html">curl</A>(1)</I>

utility can output a file in this format if run with the &quot;--cookie-jar FILENAME&quot;
option.
<P>
<P>
<A NAME="lbAM">&nbsp;</A>
<H2>ABOUT SSL CERTIFICATE CHECKS</H2>

When xymonnet tests services that use SSL- or TLS-based protocols,
it will check that the server certificate has not expired. This check
happens automatically for https (secure web), pop3s, imaps, nntps
and all other SSL-enabled services (except ldap, see LDAP TESTS 
below).
<P>
All certificates found for a host are reported in one status message.
<P>
Note: On most systems, the end-date of the certificate is limited to
Jan 19th, 2038. If your certificate is valid after this date, xymonnet
will report it as valid only until Jan 19, 2038. This is due to
limitations in your operating system C library. See
<A HREF="http://en.wikipedia.org/wiki/2038_problem">http://en.wikipedia.org/wiki/2038_problem</A> .
<P>
<P>
<A NAME="lbAN">&nbsp;</A>
<H2>LDAP TESTS</H2>

ldap testing can be done in two ways. If you just put an &quot;ldap&quot; or
&quot;ldaps&quot; tag in hosts.cfg, a simple test is performed that just verifies
that it is possible to establish a connection to the port running 
the ldap service (389 for ldap, 636 for ldaps).
<P>
Instead you can put an LDAP URI in hosts.cfg. This will cause 
xymonnet to initiate a full-blown LDAP session with the server,
and do an LDAP search for the objects defined by the URI. This
requires that xymonnet was built with LDAP support, and relies
on an existing LDAP library to be installed.  It has been tested 
with OpenLDAP 2.0.26 (from Red Hat 9) and 2.1.22.  The Solaris 8 
system ldap library has also been confirmed to work for un-encrypted 
(plain ldap) access.
<P>
The format of LDAP URI's is defined in RFC 2255. LDAP URLs look like this:
<PRE>

  <B>ldap://</B><I>hostport</I><B>/</B><I>dn</I>[<B>?</B><I>attrs</I>[<B>?</B><I>scope</I>[<B>?</B><I>filter</I>[<B>?</B><I>exts</I>]]]]

where:
  <I>hostport</I> is a host name with an optional &quot;:portnumber&quot;
  <I>dn</I> is the search base
  <I>attrs</I> is a comma separated list of attributes to request
  <I>scope</I> is one of these three strings:
    base one sub (default=base)
  <I>filter</I> is filter
  <I>exts</I> are recognized set of LDAP and/or API extensions.

Example:
  <A HREF="ldap://ldap.example.net/dc=example,dc=net?cn,sn?sub?(cn=*)">ldap://ldap.example.net/dc=example,dc=net?cn,sn?sub?(cn=*)</A>
</PRE>

<P>
All &quot;bind&quot; operations to LDAP servers use simple authentication.
Kerberos and SASL are not supported. If your LDAP server requires 
a username/password, use the &quot;ldaplogin&quot; tag to specify this, cf. 
<I><A HREF="../man5/hosts.cfg.5.html">hosts.cfg</A>(5) </I>

If no username/password information is provided, an anonymous
bind will be attempted. 
<P>
SSL support requires both a client library and an LDAP server that support LDAPv3; 
it uses the LDAP &quot;STARTTLS&quot; protocol request after establishing a connection to 
the standard (non-encrypted) LDAP port (usually port 389). It has only been
tested with OpenSSL 2.x, and probably will not work with any other LDAP library.
<P>
The older LDAPv2 experimental method of tunnelling normal LDAP traffic through an 
SSL connection - ldaps, running on port 636 - is not supported, unless someone 
can explain how to get the OpenLDAP library to support it. This method was never
formally described in an RFC, and implementations of it are non-standard.
<P>
For a discussion of the various ways of running encrypted ldap, see
<BR>

<A HREF="http://www.openldap.org/lists/openldap-software/200305/msg00079.html">http://www.openldap.org/lists/openldap-software/200305/msg00079.html</A>
<BR>

<A HREF="http://www.openldap.org/lists/openldap-software/200305/msg00084.html">http://www.openldap.org/lists/openldap-software/200305/msg00084.html</A>
<BR>

<A HREF="http://www.openldap.org/lists/openldap-software/200201/msg00042.html">http://www.openldap.org/lists/openldap-software/200201/msg00042.html</A>
<BR>

<A HREF="http://www.openldap.org/lists/openldap-software/200206/msg00387.html">http://www.openldap.org/lists/openldap-software/200206/msg00387.html</A>
<P>
When testing LDAP URI's, all of the communications are handled 
by the ldap library. Therefore, it is not possible to obtain the 
SSL certificate used by the LDAP server, and it will not show up 
in the &quot;sslcert&quot; column.
<P>
<P>
<A NAME="lbAO">&nbsp;</A>
<H2>USING MULTIPLE NETWORK TEST SYSTEMS</H2>

If you have more than one system running network tests - e.g. if your network
is separated by firewalls - then is is problematic to maintain
multiple hosts.cfg files for each of the systems.
xymonnet supports the NET:location tag in
<I><A HREF="../man5/hosts.cfg.5.html">hosts.cfg</A>(5)</I>

to distinguish 
between hosts that should be tested from different network
locations. If you set the environment variable XYMONNETWORK
e.g. to &quot;dmz&quot; before running xymonnet, then it will only
test hosts that have a &quot;NET:dmz&quot; tag in hosts.cfg. This allows
you to keep all of your hosts in the same hosts.cfg file, but
test different sets of hosts by different systems running
xymonnet.
<P>
<P>
<A NAME="lbAP">&nbsp;</A>
<H2>XYMONNET INTERNALS</H2>

xymonnet first reads the protocols.cfg file to see which network tests
are defined. It then scans the hosts.cfg file, and collects information
about the TCP service tests that need to be tested. It picks out only
the tests that were listed in the protocols.cfg file, plus the &quot;dns&quot;,
&quot;dig&quot; and &quot;ntp&quot; tests.
<P>
It then runs two tasks in parallel: First, a separate process is
started to run the &quot;xymonping&quot; tool for the connectivity tests. While 
xymonping is busy doing the &quot;ping&quot; checks, xymonnet runs all of the
TCP-based network tests.
<P>
All of the TCP-based service checks are handled by a connection
tester written specifically for this purpose. It uses only standard
Unix-style network programming, but relies on the Unix &quot;<A HREF="../man2/select.2.html">select</A>(2)&quot; 
system-call to handle many simultaneous connections happening in 
parallel. Exactly how many parallel connections are being used 
depends on your operating system - the default is FD_SETSIZE/4,
which amounts to 256 on many Unix systems.
<P>
You can choose the number of concurrent connections with the
&quot;--concurrency=N&quot; option to xymonnet.
<P>
Connection attempts timeout after 10 seconds - this can be
changed with the &quot;--timeout=N&quot; option.
<P>
Both of these settings play a part in deciding how long the testing
takes. A conservative estimate for doing N TCP tests is:
<P>
<BR>&nbsp;&nbsp;&nbsp;(1&nbsp;+&nbsp;(N&nbsp;/&nbsp;concurrency))&nbsp;*&nbsp;timeout
<P>
In real life it will probably be less, as the above formula is for
every test to require a timeout. Since the most normal use of Xymon
is to check for services that are active, you should have a lot
less timeouts.
<P>
The &quot;ntp&quot; and &quot;rpcinfo&quot; checks rely on external programs to 
do each test.
<P>
<A NAME="lbAQ">&nbsp;</A>
<H2>ENVIRONMENT VARIABLES</H2>

<DL COMPACT>
<DT>XYMONNETWORK<DD>
Defines the network segment where xymonnet is currently running.
This is used to filter out only the entries in the
<I><A HREF="../man5/hosts.cfg.5.html">hosts.cfg</A>(5)</I>

file that have a matching &quot;NET:LOCATION&quot; tag, and execute the
tests for only those hosts.
<P>
<DT>MAXMSGSPERCOMBO<DD>
Defines the maximum number of status messages that can be sent in 
one combo message. Default is 0 - no limit.
<BR>

In practice, the maximum size of a single Xymon message
sets a limit - the default value for the maximum message
size is 32 KB, but that will easily accomodate 100 status
messages per transmission. So if you want to experiment
with this setting, I suggest starting with a value of 10.
<P>
<DT>SLEEPBETWEENMSGS<DD>
Defines a a delay (in microseconds) after each 
message is transmitted to the Xymon server. The default 
is 0, i.e.  send the messages as fast as possible.
This gives your Xymon server some time to process the
message before the next message comes in. Depending on
the speed of your Xymon server, it may be necessary
to set this value to half a second or even 1 or 2 seconds.
Note that the value is specified in MICROseconds, so to
define a delay of half a second, this must be set to
the value &quot;500000&quot;; a delay of 1 second is achieved by
setting this to &quot;1000000&quot; (one million).
<P>
<DT>FPING<DD>
Command used to run the 
<I><A HREF="../man1/xymonping.1.html">xymonping</A>(1) </I>

utility. Used by xymonnet for connectivity (ping) testing.  See 
<I><A HREF="../man5/xymonserver.cfg.5.html">xymonserver.cfg</A>(5)</I>

for more information about how to customize the program that is
executed to do ping tests.
<P>
<DT>TRACEROUTE<DD>
Location of the 
<I><A HREF="../man8/traceroute.8.html">traceroute</A>(8)</I>

utility, or an equivalent tool e.g.
<I><A HREF="../man8/mtr.8.html">mtr</A>(8).</I>

Optionally used when a connectivity test fails to pinpoint the
network location that is causing the failure.
<P>
<DT>NTPDATE<DD>
Location of the 
<I><A HREF="../man1/ntpdate.1.html">ntpdate</A>(1) </I>

utility. Used by xymonnet when checking the &quot;ntp&quot; service.
<P>
<DT>RPCINFO<DD>
Location of the 
<I><A HREF="../man8/rpcinfo.8.html">rpcinfo</A>(8) </I>

utility. Used by xymonnet for the &quot;rpc&quot; service checks.
<P>
</DL>
<A NAME="lbAR">&nbsp;</A>
<H2>FILES</H2>

<DL COMPACT>
<DT>~/server/etc/protocols.cfg<DD>
This file contains definitions of TCP services that xymonnet
can test. Definitions for a default set of common services is built
into xymonnet, but these can be overridden or supplemented by
defining services in the protocols.cfg file. See 
<I><A HREF="../man5/protocols.cfg.5.html">protocols.cfg</A>(5)</I>

for details on this file.
<P>
<DT>$XYMONHOME/etc/netrc - authentication data for password-protected webs<DD>
If you have password-protected sites, you can put the usernames and 
passwords for these here. They will then get picked up automatically
when running your network tests.  This works for web-sites that use 
the &quot;Basic&quot; authentication scheme in HTTP.
See 
<I><A HREF="../man1/ftp.1.html">ftp</A>(1)</I>

for details - a sample entry would look like this
<BR>

<BR>&nbsp;&nbsp;&nbsp;machine&nbsp;<A HREF="http://www.acme.com">www.acme.com</A>&nbsp;login&nbsp;fred&nbsp;password&nbsp;Wilma1
<BR>

Note that the machine-name must be the name you use in the
<A HREF="http://machinename/">http://machinename/</A> URL setting - it need not be the one you
use for the system-name in Xymon.
<P>
<P>
<DT>$XYMONHOME/etc/cookies<DD>
This file may contain website cookies, in the Netscape HTTP
Cookie format. If a website requires a static cookie to be 
present in order for the check to complete, then you can add
this cookie to this file, and it will be sent along with the 
HTTP request. To get the cookies into this file, you can use
the &quot;curl --cookie-jar FILE&quot; to request the URL that sets
the cookie.
<P>
<DT>$XYMONTMP/*.status - test status summary<DD>
Each time xymonnet runs, if any tests fail (i.e. they result
in a red status) then they will be listed in a file name
TESTNAME.[LOCATION].status. The LOCATION part may be null. This
file is used to determine how long the failure has lasted, which
in turn decides if this test should be included in the tests done by
<I><A HREF="../man1/xymonnet-again.sh.1.html">xymonnet-again.sh</A>(1)</I>

<BR>

It is also used internally by xymonnet when determining the
color for tests that use the &quot;badconn&quot; or &quot;badTESTNAME&quot; tags.
<P>
<DT>$XYMONTMP/frequenttests.[LOCATION]<DD>
This file contains the hostnames of those hosts that should be
retested by the
<I><A HREF="../man1/xymonnet-again.sh.1.html">xymonnet-again.sh</A>(1)</I>

test tool. It is updated only by xymonnet during the normal
runs, and read by xymonnet-again.sh.
<P>
</DL>
<A NAME="lbAS">&nbsp;</A>
<H2>SEE ALSO</H2>

<A HREF="../man5/hosts.cfg.5.html">hosts.cfg</A>(5), <A HREF="../man5/protocols.cfg.5.html">protocols.cfg</A>(5), <A HREF="../man5/xymonserver.cfg.5.html">xymonserver.cfg</A>(5), <A HREF="../man1/xymonping.1.html">xymonping</A>(1),
<A HREF="../man1/curl.1.html">curl</A>(1), <A HREF="../man1/ftp.1.html">ftp</A>(1), <A HREF="../man1/fping.1.html">fping</A>(1), <A HREF="../man1/ntpdate.1.html">ntpdate</A>(1), <A HREF="../man8/rpcinfo.8.html">rpcinfo</A>(8)
<P>
<P>

<HR>
<A NAME="index">&nbsp;</A><H2>Index</H2>
<DL>
<DT><A HREF="#lbAB">NAME</A><DD>
<DT><A HREF="#lbAC">SYNOPSIS</A><DD>
<DT><A HREF="#lbAD">DESCRIPTION</A><DD>
<DT><A HREF="#lbAE">GENERAL OPTIONS</A><DD>
<DT><A HREF="#lbAF">OPTIONS FOR TESTS OF THE SIMPLE TCP SERVICES</A><DD>
<DT><A HREF="#lbAG">OPTIONS FOR THE PING TEST</A><DD>
<DT><A HREF="#lbAH">OPTIONS FOR HTTP (WEB) TESTS</A><DD>
<DT><A HREF="#lbAI">OPTIONS FOR SSL CERTIFICATE TESTS</A><DD>
<DT><A HREF="#lbAJ">DEBUGGING OPTIONS</A><DD>
<DT><A HREF="#lbAK">INFORMATIONAL OPTIONS</A><DD>
<DT><A HREF="#lbAL">USING COOKIES IN WEB TESTS</A><DD>
<DT><A HREF="#lbAM">ABOUT SSL CERTIFICATE CHECKS</A><DD>
<DT><A HREF="#lbAN">LDAP TESTS</A><DD>
<DT><A HREF="#lbAO">USING MULTIPLE NETWORK TEST SYSTEMS</A><DD>
<DT><A HREF="#lbAP">XYMONNET INTERNALS</A><DD>
<DT><A HREF="#lbAQ">ENVIRONMENT VARIABLES</A><DD>
<DT><A HREF="#lbAR">FILES</A><DD>
<DT><A HREF="#lbAS">SEE ALSO</A><DD>
</DL>
<HR>
This document was created by
<A HREF="/cgi-bin/man/man2html">man2html</A>,
using the manual pages.<BR>
Time: 09:25:34 GMT, January 07, 2014
</BODY>
</HTML>
